Peer-to-peer data communication between different applications

ABSTRACT

Examples described herein include systems and methods for synchronizing applications that target different software development kits (“SDK”). The system can execute a bridge application that registers an implementation of a content provider class. This allows the bridge application to communicate with a first application targeting a first SDK. The bridge application can also register to send and receive implicit broadcasts. After the bridge application verifies the request, it can broadcast to a second cluster of applications registered with an operating system to receive implicit broadcasts. Similarly, the bridge application can receive implicit broadcasts and synchronize those requests with a first cluster of applications by using the implemented content provider methods.

BACKGROUND

Applications on a user device, such as a laptop, commonly communicatewith one another to synchronize information. This is particularly truefor applications in a Mobile Device Management (“MDM”) or EnterpriseMobility Management (“EMM”) system. In those systems, providers canallow employees to access multiple different applications based on asingle user authentication, and actions in one application can impactfunctionality in another. For single-sign-on (“SSO”) and othermanagement features to function correctly, applications on the userdevice need to synchronize information amongst themselves.

ANDROID applications have commonly used implicit broadcasts for datasynchronization. A first application can broadcast a request that isreceived by all other applications that have registered with theoperation system (“OS”) to receive the broadcasts. The receivingapplications respond to those requests, such as push and pull requests,to send and receive data updates.

However, newer OS versions and software development kits (“SDK”) canprevent applications from registering with the OS to receive implicitbroadcasts. For example, ANDROID 8.0 SDK 26 and above disallowsregistering receivers for implicit broadcasts. An application that doesnot register a broadcast receiver will not receive an implicit broadcastsent by another application.

This can break synchronization of applications on the user device. Forexample, for ANDROID 8.0 and higher, first applications that target afirst SDK (26 or greater) will not receive implicit broadcasts fromsecond applications targeting a second SDK (25 or lower). The firstapplications can use some other protocol to synchronize amongstthemselves, but this still creates a backwards compatibility issue. Twoapplication clusters targeting different SDKs will only synchronizeamongst themselves and not with each other.

As a result, a need exists for systems and methods for synchronizingstates between clusters of applications that target different SDKs.

SUMMARY

Examples described herein include systems and methods for peer-to-peersynchronization between applications targeting different SDKs. A bridgeapplication can execute on a processor of a device, such as a laptop,tablet, phone, or computer. The bridge application can register apeer-to-peer (“P2P”) provider with the OS. The P2P provider canimplement content provider, which can be a class available for theANDROID operating system in an example, to use the content providermethods for P2P synchronization purposes. For example, an update methodcan act as a push and a query method can act as a pull. The contentprovider methods can be used for synchronization by a first applicationtargeting a first SDK, such as SDK 26 or later for ANDROID. The firstSDK disallows registration of a receiver with the OS for receivingimplicit broadcasts.

However, the bridge application can also register, with the OS, areceiver that receives implicit broadcasts. Implicit broadcasts can beused to synchronize data with various requests for a second application.The second application can target a second SDK, such as SDK 25 or belowfor ANDROID.

The bridge application can receive a request from the first application.The request can be received by the P2P provider registered by the bridgeapplication. The request can be a push or pull request, in the form ofan update or query.

The bridge application can verify a signature of the request prior toperforming the update or query. The signature can exist as a key that isprovided in a P2P channel used by content provider. The channel can bespecifically implemented by the P2P provider. The signature can becompared against a whitelist of recognized signatures or checked againstkeys that form a potential key pair. Other verification can also includechecking a channel ID and other aspects of the request itself, such as aname and address of a P2P provider that sent the request. Theseverification steps can be performed by the bridge application's P2Pprovider, in an example.

In addition to verification, the bridge application can check that therequest is non-redundant. This can involve comparing a time stamp of therequest against time stamps of local data or of other requests thebridge application has received. If the request is non-redundant, thebridge application can perform the request on its own local data. Forexample, the bridge application can update data in response to a push orreturn data to the first application in response to a pull.

If the request is verified and non-redundant, the bridge application canalso synchronize the request by broadcasting to a second application.The second application can receive the broadcast by preregistering areceiver with the OS. The second application targets an SDK that allowsregistration to receive implicit broadcasts. By doing this, the bridgeapplication can allow first and second application clusters tosynchronize between each other, even when each cluster targets differentSDKs and uses different protocols to synchronize.

These stages can be performed as part of a computer-implemented method.Alternatively, they can execute in a device or system that retrievesinstructions from memory for execution with a processor. These stagescan be stored on a non-transitory, computer-readable medium forexecution by a processor.

Both the foregoing general description and the following detaileddescription are exemplary and explanatory only and are not restrictiveof the examples, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of an exemplary method for managing firmware of agroup of user devices associated with an enterprise.

FIG. 2A is a flowchart for synchronization between applications usingimplicit broadcasts.

FIG. 2B is an exemplary flowchart for synchronization betweenapplications implementing content provider.

FIG. 3A is an exemplary illustration of synchronization betweenapplication clusters.

FIG. 3B is an exemplary illustration of synchronization betweenapplication clusters.

FIG. 3C is an exemplary illustration of synchronization betweenapplication clusters.

FIG. 3D is an exemplary illustration of synchronization betweenapplication clusters.

FIG. 4A is an exemplary flowchart for handling and synchronizing a pushrequest.

FIG. 4B is an exemplary flowchart for handling and synchronizing a pullrequest.

FIG. 5 is an exemplary illustration of system components.

DESCRIPTION OF THE EXAMPLES

Reference will now be made in detail to the present examples, includingexamples illustrated in the accompanying drawings. Wherever possible,the same reference numbers will be used throughout the drawings to referto the same or like parts.

Examples described herein include systems and methods for P2Psynchronization of applications that target different SDKs in an OS suchas ANDROID. A user device, such as a tablet, phone, or computer, caninclude multiple applications that synchronize with one another.Synchronization can be important for application features that depend onevents, status, or activity in another application. Applications alsosynchronize for security processes, such as SSO, password-basedencryption (“PBE”), and other security or authentication processes.

To synchronize, ANDROID applications have commonly used implicitbroadcasts as a background process. Applications register a receiverwith the OS to receive the broadcasts. ANDROID SDK 25 and below allowsfor registering receivers to receive implicit broadcasts. However, inANDROID 8.0, SDK 26 and above disallow registration to receive implicitbroadcasts. This means applications that target newer SDK versions willnot listen for implicit broadcasts and will not synchronize correctlywith existing applications relying on implicit broadcasting. Even thoughapplications targeting SDK 26 or higher can communicate with oneanother, they are not backwards compatible with applications targetingSDK 25 or lower, which rely on implicit broadcasts.

To solve this problem, bridge applications are introduced that cancommunicate with applications targeting different SDKs. This can allowfor synchronization across applications groups. A first group ofapplications can target SDK 26 and above. These are typically newerapplications. They can synchronize by using messaging in a contentprovider class rather than through implicit broadcasts. A. second groupof applications, typically legacy applications, can target SDK 25 andbelow. The second group of applications still relies on implicitbroadcasts for synchronization.

The bridge application can compile SDK 26 or above but target SDK 25 orbelow. The bridge application can register with the OS both a receiverfor implicit broadcasts and a P2P implementation of content provider.The latter is referred to as a P2P provider. The first application canmake requests to any P2P implementation of content provider that isregistered with the OS. By registering the P2P provider, the bridgeapplication can receive those requests and can similarly make requeststo other applications that implement content provider for P2P purposes,such as the first application.

The bridge application's P2P provider can receive the request from thefirst application. The P2P provider can then verify that it is validbefore fulfilling the request. This can include comparing a signature ofthe request against a whitelist. For example, managed or enterpriseapplications can use common signatures when communicating with oneanother. The bridge application can also perform other channel specificactions, such as checking that SSO is enabled and the SDK isinitialized.

After verification, the bridge application can synchronize the requestby broadcasting it to a second application that targets SDK 25 or below.The second application can listen for implicit broadcasts. To furthersynchronize, the second application can rebroadcast the request to otherapplications registered to receive the broadcasts. This effectivelyallows for the transfer of data between the first and secondapplications even though they target different SDKs that cause implicitbroadcast incompatibility.

FIG. 1 is an example method for P2P synchronization among first andsecond applications that target different SDKs. A bridge applicationexecuting on the user device can facilitate synchronization between thefirst and second applications. The first application can target an SDKthat disallows registering for implicit broadcasts, such as ANDROID SDK26 or higher. The first application instead communicates with otherapplications using a content provider class of ANDROID, in an example.The second application does not implement the content provider class,and instead relies on implicit broadcasts to communicate with otherapplications on the user device.

At stage 105, the bridge application can register a P2P provider withthe OS. The P2P provider can implement the content provider class in aP2P context. The P2P provider can act as a transport layer to facilitatecommunications, such as update and query commands, on P2P channels.Using content provider, the P2P provider can send and receiveinformation with other applications.

In one example, the bridge application registers the P2P provider atstage 105 by identifying the P2P provider as a receiver and provider inits manifest. An example manifest is shown below.

<receiver android: name=“com.emm.sdk.p2p.P2PReceiver”> <intent-filter><action android:name= “com.emm.sdk.p2p.P2PProvider” </receiver><provider android:name=“com.emm.sdk.p2p.P2PProvider”android:authorities=${applicationID}.p2p android:enabled=“true”android:multiprocess=“false” android:exported=“true”> </provider>

Registering the P2P provider can enable communication with the firstapplication. To synchronize, the first application can retrieve theregistered P2P providers, including that of the bridge application, fromthe OS. Then the first application can send requests to the P2Pproviders.

At stage 107, the bridge application can also register with the OS toreceive implicit broadcasts. This can enable the bridge application tosend and receive communications with applications that use implicitbroadcasts to synchronize, including the second application. Themanifest can include a registration string that the SDK uses to registerthe broadcast receiver with the OS. When the second application sends abroadcast, the receiver registered for the bridge application canreceive that broadcast.

To utilize both the P2P provider and broadcast receivers, the bridgeapplication can compile SDK 26 or higher but target SDK 25 or lower.This configuration can be specified in the manifest of the bridgeapplication. Compiling SDK 26 or higher can allow the bridge applicationand first application to securely communicate using the P2P providerregistered in stage 105. However, by targeting SDK 25 or lower, thebridge application can also still receive implicit broadcasts based onthe registration of stage 107. As a result, the bridge application cancommunicate with both the second application, which relies on implicitbroadcasts, and the first application, which communicates using the P2Pprovider's implementation of content provider. Receiving bothcommunication types can allow the bridge application to bridgesynchronization between clusters of old applications and clusters of newapplications.

At stage 110, the bridge application can receive a request at the P2Pprovider from a first application that targets a first SDK that does notallow implicit broadcasts. The request can be a push or a pull request.Content provider includes an update command that can be implemented asthe push request. The update can cause the bridge application to writedata to a resource, such as a table of a database. Similarly, a querycommand in content provider can act as a pull request. The query cancause the bridge application to return data.

The P2P provider can specify which content provider channels are used inthe requests. For example, the content provider command can be sent on afirst channel, and a signature (such as a key) can be sent on anotherchannel.

At stage 115, the bridge application can verify that the request shouldbe synchronized by verifying a signature of the request. Becauseuntrusted applications can also communicate using content provider, theverification at stage 115 can be used to ensure that the request iscoming from a recognized application. This can prevent synchronizationfrom breaking based on communications from unrelated applications orfrom malicious applications.

The verification can include checking a signature that is included withthe request. The signature can be an authority string that identifiesthe P2P provider of the first application. The P2P provider of thebridge application can verify that it should synchronize with the firstapplication. To do this, the signature can be compared against awhitelist, in an example. The signature can be specific to applicationstrusted by an enterprise or EMM provider. For example, managedapplications for a EMM provider can have known signatures that areincluded in the whitelist stored at the bridge application or itsregistered P2P provider. A management server can update the whitelist(at the bridge application or P2P provider) to manage which applicationscan synchronize with one another.

In one example, the first application includes a key as the signature.The key can be provided in one of seven content provider channels. Thebridge application can verify the key by determining that the correctchannel is used and that the bridge application or P2P provider has avalid key pair. The EMM provider can configure the bridge application orP2P provider to recognize multiple signatures and synchronize amongstmultiple defined groups of applications, including the firstapplication.

In one example, verifying the signature can be performed after otherless time-intensive verification steps. The P2P provider can beconfigured to perform the signature check last in case a simplerverification shows a request should be ignored. For example, the bridgeapplication can first check for a uniform resource information (“URI”)match, then a channel ID match, and then a signature match.

In one example, the URI can identify the channel and the request.Alternatively, the URI can be a string of characters that identifies theP2P provider and a resource to update or request. For example, the URIcan include identification of an individual row in a table. Data accessmethods of content provider can have a content URI as an argument,allowing the bridge application or other application receiving therequest to determine the table, row, or file to access. If the URI isdifferent than expected by the bridge application, the bridgeapplication can decline synchronization.

The channel ID can identify which channel or channels the firstapplication is attempting to communicate over. In one example, thechannel ID is part of the URI. The content provider class can includeseven different channels. If the first application is not communicatingon a channel expected by the bridge application, the bridge applicationcan decline synchronization.

At stage 125, the bridge application can determine that the request isnon-redundant. In one example, the bridge application can do this bychecking a request identifier and a request date. The request identifiercan be specific to the application sending the request or can bespecific to the request itself For example, the request identifier caninclude the URI, channel ID, and signature. The request date canindicate when the request was sent. The bridge application can check ahistory of requests to determine if it has received the same requestidentifier with an earlier date. If so, the bridge application canignore the request as redundant.

Otherwise, at stage 130, the bridge application can synchronize therequest by broadcasting to the second application using an implicitbroadcast. If the request is a push, then the bridge application canbroadcast the push out to the second application and other applicationsthat are listening for implicit broadcasts. If the request is a pull,then the bridge application can broadcast a pull request to the firstapplication and receive back data for forwarding to the firstapplication. In this way, the bridge application can push or pull datafrom both first and second applications that target different SDKs andcannot directly synchronize.

FIG. 2A is a flowchart that illustrates steps involved with an implicitbroadcast. A bridge application can broadcast a pull operation tosynchronize with applications targeting SDK 25 and lower. Applicationsthat have registered to receive implicit broadcasts can receive thebroadcast and send data to the bridge application. Although FIG. 2Ashows example stages between the bridge application and the secondapplication (APP 2), these stages can apply to any two applicationscapable of using implicit broadcasts to synchronize.

At stage 210, the bridge application can make an implicit broadcast onthe discovery channel. The broadcast can include a pull request and cancontain the communication information. This can allow registeredapplications to receive the broadcast. The OS can track whichapplications have registered to receive implicit broadcasts. The OS canalso route the broadcasts to those applications or provide the bridgeapplication with an address to use.

In one example, a first application that targets an incompatible SDKcannot receive the broadcast. For example, if the first applicationtargets ANDROID 8 SDK 26 or higher, it cannot register a receiver withthe OS. Therefore, the broadcast of stage 210 will not be sent to thefirst application. Instead, the bridge application can use a P2Pimplementation of content provider, in an example. This can includeregistering a P2P provider in the bridge application. The P2P providercan implement content provider and use its methods in a P2Psynchronization context. This approach is compatible with ANDROID 8 SDK26 and will be discussed later regarding FIG. 2B.

Continuing with FIG. 2A, at stage 215, the second application, havingregistered with the SDK to receive implicit broadcasts, receives thepull request. But before performing the pull, the second application canverify the request. This can include verifying a signature, such as astring or other key included with the request, against a whitelist. Itcan also include other verifications, as will be discussed with regardto FIGS. 4A and 4B.

After verification, at stage 220 the second application can start up anintent service to process the request. In ANDROID, an intent is aspecific action. The second application can start an intent service toresolve the pull request by fetching local data at stage 230. Forexample, the intent service can retrieve data from a table.

At stage 235, the second application can send data back to the bridgeapplication. The bridge application can determine if the data should bemerged with the local data. For example, the bridge application candetermine if the data is newer than existing data at the bridgeapplication. if so, at stage 240, the bridge application can merge thedata sent through the intent with the local data existing at the bridgeapplication.

However, the first application, which targets SDK 26 or higher, cannotcommunicate using implicit broadcasts in this manner. Instead, thebridge application can issue a pull request through use of the P2Pprovider, as shown in FIG. 2B.

FIG. 2B illustrates exemplary stages for sending a pull request usingP2P providers, which can be P2P implementations of content provider.Although this example shows a bridge application making a push requestto a first application, the stages can apply to any two applicationsutilizing a P2P implementation of content provider for synchronizationpurposes.

At stage 250, the bridge application can retrieve available P2Pproviders. The OS returns the names and addresses of other applicationsthat have implemented the P2P protocol on top of content provider. inone example, the OS identifies the P2P providers associated with thoseapplications. As is the case with the bridge application, otherapplications can register a P2P provider with the OS by identifying theP2P provider in a manifest. This can allow the OS to identify the P2Pproviders to the bridge application.

The OS can identify the P2P provider of the first application. The firstapplication can include a manifest that registers its P2P provider withthe OS. That can allow the bridge application to retrieve that P2Pprovider in stage 250.

At stage 255, the bridge application can send the pull request byissuing a query command to the P2P provider of the first application.The query command can be an implemented method of content provider.Rather than sending a broadcast to registered receivers, as done instage 210 of FIG. 2A, applications targeting SDK 26 and higher can relyon content provider methods to either query or update otherapplications. In one example, content resolver can provide access to theP2P provider of the first application. The content resolver can directthe bridge application's request to the P2P provider without knowing theimplementation of content provider it is interacting with. The URI canspecify the P2P provider of the first application. The content resolvercan be based on the content resolver class in ANDROID, which is part ofANDROID's content package.

At stage 260, the first application can verify that the request from thebridge application is trusted. This can include verifying a signature.It can also include other verifications, such as verifying that thechannel ID and URI are recognized by the P2P provider.

At stage 265, the first application can retrieve the data requested bythe query from the bridge application. This can include retrieving afile or data from a table in a database. The first application canreturn a cursor to the retrieved data that allows the bridge applicationto access that data. Then, at stage 270, the bridge application canmerge the data with its own.

FIGS. 3A-3D illustrate examples of how bridge applications can be usedto facilitate synchronization between clusters of applications thattarget different SDKs. FIG. 3A illustrates a first cluster 310 ofapplications that utilize a first version of P2P synchronization, and asecond cluster 330 that utilizes a second version of P2Psynchronization. The first version can rely on implicit broadcasts. Forexample, the first cluster 310 of applications can all target SDK 25 orbelow. The second version of P2P synchronization can be based on a P2Pimplementation of content provider. For example, the second cluster 330of applications can all target SDK 26 or above.

As shown in FIG. 3A, these two clusters 310 and 330 cannot directlysynchronize with each other. Instead, they are both able to communicatewith a bridge cluster 320, which can contain multiple bridgeapplications. The bridge applications can compile SDK 26 or higher andtarget SDK 25 or lower. The bridge applications can therefore registerto listen for implicit broadcasts from the first cluster 310. However,compiling the newer SDK can also allow the bridge applications toregister a P2P provider and make and receive content provider commandsto interact with the second cluster 330.

FIG. 3B is an example illustration showing synchronization of a pushrequest. In this example, the push request originates from App 1 of thefirst cluster 310. App 1 uses an implicit broadcast to make the request,meaning only those applications that can receive an implicit broadcastwill directly receive the request. In this example, Apps 2, 3, and 4receive the request because they target SDK 25 or lower have allregistered to receive implicit broadcasts. However, Apps 5 and 6 do notdirectly receive the broadcast from App 1 because the second cluster 330targets SDK 26 or higher and cannot register for implicit broadcasts.

When Apps 3 and 4 of the bridge cluster 320 receive the broadcast, theycan resend the request using both the first and second versions of P2Psynchronization. In this example, they can send an update command toApps 5 and 6 using the P2P provider. Apps 5 and 6 can include manifeststhat register the P2P provider. This allows Apps 3 and 4 of the bridgecluster 320 to communicate with Apps 5 and 6. As a result, the pushrequest originating as a broadcast from App 1 is synchronized with Apps5 and 6 as an update request from Apps 3 and 4.

FIG. 3C is an example illustration of a pull request made by App 3 ofthe bridge cluster 320. App 3 can broadcast the pull request to Apps 1and 2 of the first cluster 310. App 3 can also send a query command tothe P2P providers of Apps 4, 5, and 6. This can allow App 3 tosynchronize with all of the apps from the first cluster 310, bridgecluster 320, and second cluster 330.

FIG. 3D is an example illustration of a pull request made by App 1 ofthe first cluster 310. App 1 can broadcast the request to Apps 2, 3, and4, which have all registered to receive the broadcasts. Although App Icannot pull directly from Apps 5 and 6 of the second cluster 320, thedata from Apps 5 and 6 can be sent from App 3 or 4. For example, becauseApp 3 of the bridge cluster 330 already pulled data from Apps 5 and 6 aspart of the pull request of FIG. 3C, the response of App 3 in FIG. 3Dcan include that data. In one example, App 3 can make an additional pullrequest, such as shown in FIG. 3C, prior to completing the query bysending data back to App 1 in FIG. 3D. This can ensure that thesynchronization is backwards compatible between the first cluster 310and second cluster 330.

FIG. 4A is an example illustration of stages performed by a P2P providerfor handling a pull request. The stages of FIG. 4A can be performed by abridge application or another application that uses content provider tosynchronize. For example, the bridge application can register the P2Pprovider with the OS by including a string in the manifest of the bridgeapplication. This can allow other applications to contact the bridgeapplication using content provider commands sent to the P2P provider.

In one example, the stages in the P2P Transportation Layer V2 box areperformed by the P2P provider. At stage 405, the P2P provider canreceive the push request from a first application using the contentprovider to synchronize. For example, the first application can send apush request formatted as follows: update(URI, content values, channelID, null).

Before merging data, the P2P provider can perform various stages toensure that the request is trusted and should be executed. At stage 410,the P2P provider can determine if there is a URI match. The URI canspecify a resource location to retrieve or update. The P2P provider candetermine if the URI corresponds to a resource at the bridgeapplication. If so, then verification can move to stage 415. If not,then the P2P provider can exit at stage 425 without updating local dataof the bridge application.

At stage 415, the P2P provider can determine if a channel ID matchexists. Content provider can utilize one or more of seven channels witha request. However, the P2P provider can be configured to use aparticular channel for a request type. Therefore, the P2P provider canverify that the correct channel ID is being used for the request priorto proceeding any further. If the channel ID does not match the expectedchannel of the P2P provider, then the P2P provider can exit at stage 425without updating local data of the bridge application.

If the channel ID does match, then the P2P provider can proceed to stage420. At stage 420, the P2P provider can determine if the requestincludes a recognized signature. The signature can be used to ensurethat the requesting application is associated with the same enterpriseor EMM provider as the receiving application (in this example, thebridge application). Because a signature verification can be more timeintensive than the URI match or channel ID match, stage 420 can occurafter stages 410 and 415 in an example. If the requesting application isusing the SDK specified by the EMM provider, it can send the samesignature recognized by the bridge application, which can compile thesame SDK.

In one example, the signature can be compared against a whitelist at thebridge application. This can allow the EMM provider to control whichapplications synchronize across multiple SDKs, each of which can includeits own unique signature. For example, an EMM provider or enterprise canconfigure a P2P provider to recognize multiple keys, then specify thatP2P provider in the manifest of the bridge application.

The signature can be a string specified in the P2P provider of therequesting application (in this example, the first application).Alternatively, the signature can be a key. Verification of thesignature, therefore, can include determining if the P2P provider of thebridge application has access to a matching key.

If the signature matches, then the P2P provider can proceed fromverification to channel-specific stages at stage 430. At stage 430, thebridge application can resolve the data type of the request. This caninclude performing a channel-specific action. For example, the bridgeapplication can determine that SSO is enabled, as the channel ID cancorrespond to a channel that is used to synchronize between applicationsthat utilize SSO.

The P2P provider can determine if the SDK needs to be initialized forcommunication on the channel. If so, the P2P provider can initialize theSDK. Other channel-specific stages can also be executed. For example,the P2P provider can unlock a database needed to fulfill the request.The P2P can determine which database to unlock based on the URI of therequest, in one example.

Stage 435 illustrates an alternate scenario involving a request that isreceived at the broadcast receiver of the bridge application. Forexample, a second application targeting SDK 25 or below can broadcast apush request. Because the bridge application has registered a receiverwith the OS, it can receive the implicit broadcast at stage 435.

After stages 430 and 435, the bridge application can determine whetherthe request should be synchronized. Similar stages can be applied to therequest, whether it is received from the P2P provider or the broadcastreceiver, in an example.

At stage 440, the bridge application can retrieve local data. This canbe done in one example to ensure that the data sent from the firstapplication is not outdated before performing the update. The bridgeapplication can locate a local resource implicated by the push request,such as data in a table. In one example, the URI can specify theresource location. Alternatively, the URI identifies a P2P channel thatcontains identification of the resource to update. In still anotherexample, the request can implicate a type of information that the bridgeapplication interprets and locates.

At stage 442, the bridge application can verify that the request data isnewer than existing local data before updating in response to the pushrequest. For example, the push request data can have a date and timestamp. Similarly, the local data can have a date and time stamp. If thelocal data is more recent than the date and time of the pushed data,then the request can be ignored.

Otherwise, at stage 444, the bridge application can store the data byperforming the update. The new data can be indicated by the contentvalues portion of the push request, in an example.

If data storage was successful, then at stage 446 the bridge applicationcan determine whether to synchronize the request with a differentapplication cluster. This can include determining whether the data isredundant by comparing the request with a buffer of prior requests. Thedetermination can also or alternatively rely on the time stampcomparison of stage 442, since old data can be ignored and notsynchronized.

If the data is new, then the bridge application can send the pushrequest to a different application cluster. For example, at stage 448,if the request was from the P2P provider (using SDK version 2), then thebridge application can synchronize with a second application by implicitbroadcast. The second application can be registered with the OS toreceive the broadcast. In one example, this can allow the secondapplication and the bridge application to synchronize the request with asecond cluster of applications targeting SDK 25 or below even though therequest originated from a first application targeting SDK 25 or above.

Similarly, if the request originates from the broadcast receiver, thenat stage 450 the push request can be sent to a P2P provider of the firstapplication. The first application can register the P2P provider withthe OS. The bridge application's P2P provider can receive names andaddresses of the other registered P2P providers, including that of thefirst application. Then, at stage 450, the bridge application can send apush request formatted as an update command to the first application.This can synchronize the first application, targeting an SDK of 26 orgreater, even though the request originated from the second application,targeting an SDK of 25 or below. In this way, a request originating in asecond cluster can synchronize a first cluster of applications.

FIG. 4B is an example illustration of stages performed by a bridgeapplication to handle a pull request. In one example, the P2P providerregistered by the bridge application performs the stages of the P2PTransportation Layer V2. The bridge application itself can perform thelocal data operations of the Channel Layer.

At stage 455, the pull request can be sent by the first application tothe bridge application's P2P provider. The pull request can be a querycommand in content provider, formatted as follows: query(URI, null,channel ID, null, null).

The P2P provider can verify the pull request using similar stages tothose described in FIG. 4A for the push request. For example, at stage460, the P2P provider can verify a URI match. At stage 465, the P2Pprovider can verify a channel ID match. At stage 470, the P2P providercan verify a signature match. If any of these verifications fail, theP2P provider can exit by returning a null value at stage 475.

Otherwise, the P2P provider can execute channel-specific tasks at stage480. For example, the P2P provider can determine if the SDK needsinitialization on the channel and can verify that SSO is enabled. Thenthe channel can resolve what data type is being pulled based in part onthe channel ID.

At stage 485, the P2P provider can execute the query and retrieve thelocal data from the resource identified by the pull request. The P2Pprovider can ensure that the request is new before returning therequested data. To do this, the P2P provider can compare a timestamp ofthe pull request to a timestamp of the local data. If the local data ismore recent than the pull request, then the P2P provider can return nullat stage 475. Otherwise, the queried data is returned at stage 497.

The bridge application can also synchronize the pull request with asecond application that targets SDK 25 or below. After determining therequest is new and nonredundant, the bridge application can broadcast apull request that is received by the second application. The secondapplication can have a receiver registered with the OS to receiveimplicit broadcasts. In one example, the bridge application can performa broadcast between stages 485 and 497. This can allow the bridgeapplication to pull data from the second application cluster beforereturning data to the first application, which can be part of the firstapplication cluster.

FIG. 5 is an example illustration of components of a device 510 forperforming synchronization between application clusters. The device canbe any physical processor-enabled device, such as a phone, laptop, orpersonal computer. The processor 520 can be one or more processors thatinteract with instructions in a non-transitory, computer-readablemedium, such as memory 530. Memory 530 is a physical memory, such as RAMor a disk drive.

Various applications can execute on the device 510. For example, thefirst application cluster 310, second application cluster 330, andbridge applications 320 can all execute on the device 510. The clustersof applications, for purposes of this disclosure, can be based on thetargeted SDK 550. As discussed above, the SDK targeted can impact whichapplications can talk to one another. Applications of the first cluster310 can all communicate with each other based on a P2P provider thatimplements content provider. Applications of the second cluster 330 cancommunicate with one another based on implicit broadcasts.

The applications of the first, bridge, and second clusters 310, 320, and330 can be provided by one or more companies. In one example, some orall of the applications 310, 320, 330 are installed on the device 510based on enrollment of the device in an EMM system. However, an EMMsystem is not required for practice of examples disclosed herein.

An OS 540, such as ANDROID, can be installed on the device 510. The OS540 can include multiple different SDKs 550, each of which can allowdifferent functionality for the applications 310, 320, 330 that executeon the device 510. Each application 310, 320, 330 can target a specificSDK 550. In one example, the bridge applications 320 can target ANDROIDSDK 25 or lower, while also compiling SDK 26 or higher. The bridgeapplications 320 can register a broadcast receiver 322 with the OS 540.This can allow the bridge applications to use implicit broadcasts tosend and receive requests to and from the second application cluster330. The bridge applications 320 can also register a P2P provider 324with the OS 540. This can allow the bridge applications 320 to usecontent provider functions to communicate with the first applicationcluster 310.

The example of SDK 25 and below versus SDK 26 and above is exemplary andthe invention applies to other contexts. The examples can apply to otheroperating systems in addition to ANDROID. Additionally, differentversions of ANDROID can impose different restrictions on the SDKs usedor available. In addition, the described techniques of the bridgeapplication 320 can be used even when implicit broadcasts are used tocommunicate between applications 310 and 330. For example, even when thefirst and second clusters 310 and 330 can each register to receiveimplicit broadcasts, the second cluster 330 might instead register a P2Pprovider. In that instance, the bridge application 320 can facilitatesynchronization between the two clusters 310 and 330. Therefore, theexamples can be useful even when two application clusters 310 and 330target the same SDK.

The bridge applications 320 can have other purposes besides justfacilitating synchronization between disparate application clusters 310and 330. For example, the bridge applications 320 can be enterpriseapplications, such as an email client or word processing application. inother words, the bridge applications 320 can include applications that auser would install for normal work or entertainment purposes. But thesebridge applications 320 can ensure reverse compatibility forsynchronization between newer applications targeting SDK 26 and aboveand older applications targeting SDK 25 and below.

Other examples of the disclosure will be apparent to those skilled inthe art from consideration of the specification and practice of theexamples disclosed herein. Though some of the described methods havebeen presented as a series of steps, it should be appreciated that oneor more steps can occur simultaneously, in an overlapping fashion, or ina different order. The order of steps presented is only illustrative ofthe possibilities and those steps can be executed or performed in anysuitable fashion. Moreover, the various features of the examplesdescribed here are not mutually exclusive. Rather any feature of anyexample described here can be incorporated into any other suitableexample. It is intended that the specification and examples beconsidered as exemplary only, with a true scope and spirit of thedisclosure being indicated by the following claims.

1.-20. (canceled)
 21. A method for synchronizing between applicationsthat target different software development kits (“SDK”) of an operatingsystem (“OS”), comprising: registering with the OS at least: apeer-to-peer (“P2P”) provider of a bridge application, wherein the P2Pprovider facilitates communications on a P2P channel; and a receiverthat receives implicit broadcasts; receiving, at the bridge application,a request from a first application, wherein the first applicationtargets a first SDK that disallows registration for receiving implicitbroadcasts; and synchronizing the request by broadcasting to a secondapplication that targets a second SDK that allows registration forimplicit broadcasts.
 22. The method of claim 1, wherein the bridgeapplication verifies a signature of the request prior to synchronizingthe request.
 23. The method of claim 1, wherein the bridge applicationchecks that the request is non-redundant prior to synchronizing therequest.
 24. The method of claim 1, wherein the request is a pushrequest, and wherein the bridge application updates its data in responseto the push request.
 25. The method of claim 1, further comprisingverifying a uniform resource indicator (“URI”) and channel ID prior tosynchronizing the request.
 26. The method of claim 1, wherein the bridgeapplication includes a manifest that targets the second SDK but alsocompiles the first SDK.
 27. The method of claim 1, further comprising:receiving an implicit broadcast at the bridge application from thesecond application; and sending a second request to a P2P provider ofthe first application to carry out a command.
 28. A non-transitory,computer-readable medium comprising instructions that, when executed bya processor, perform stages for synchronizing between applications thattarget different software development kits (“SDK”), the stagescomprising: registering with the OS at least: a peer-to-peer (“P2P”)provider of a bridge application, wherein the P2P provider facilitatescommunications on a P2P channel; and a receiver that receives implicitbroadcasts; receiving, at the bridge application, a request from a firstapplication, wherein the first application targets a first SDK thatdisallows registration for receiving implicit broadcasts; andsynchronizing the request by broadcasting to a second application thattargets a second SDK that allows registration for implicit broadcasts.29. The non-transitory, computer-readable medium of claim 28, whereinthe bridge application verifies a signature of the request prior tosynchronizing the request.
 30. The non-transitory, computer-readablemedium of claim 28, wherein the bridge application checks that therequest is non-redundant prior to synchronizing the request.
 31. Thenon-transitory, computer-readable medium of claim 28, wherein therequest is a push request, and wherein the bridge application updatesits data in response to the push request.
 32. The non-transitory,computer-readable medium of claim 28, the stages further comprisingverifying a uniform resource indicator (“URI”) and channel ID prior tosynchronizing the request.
 33. The non-transitory, computer-readablemedium of claim 28, wherein the bridge application includes a manifestthat targets the second SDK but also compiles the first SDK.
 34. Thenon-transitory, computer-readable medium of claim 28, the stages furthercomprising: receiving an implicit broadcast at the bridge applicationfrom the second application; and sending a second request to a P2Pprovider of the first application to carry out a command.
 35. A systemfor synchronizing application clusters that target different softwaredevelopment kits (“SDK”), comprising: a memory storage including anon-transitory, computer-readable medium comprising instructions; and aprocessor that executes the instructions to carry out stages of a bridgeapplication, the stages comprising: registering with the OS at least: apeer-to-peer (“P2P”) provider of the bridge application, wherein the P2Pprovider facilitates communications on a P2P channel; and a receiverthat receives implicit broadcasts; receiving, at the bridge application,a request from a first application, wherein the first applicationtargets a first SDK that disallows registration for receiving implicitbroadcasts; and synchronizing the request by broadcasting to a secondapplication that targets a second SDK that allows registration forimplicit broadcasts.
 36. The system of claim 35, wherein the bridgeapplication verifies a signature of the request prior to synchronizingthe request.
 37. The system of claim 35, wherein the bridge applicationchecks that the request is non-redundant prior to synchronizing therequest.
 38. The system of claim 35, wherein the request is a pushrequest, and wherein the bridge application updates its data in responseto the push request.
 39. The system of claim 35, wherein the bridgeapplication includes a manifest that targets the second SDK but alsocompiles the first SDK.
 40. The system of claim 35, the stages furthercomprising: receiving an implicit broadcast at the bridge applicationfrom the second application; and sending a second request to a P2Pprovider of the first application to carry out a command.